Skip to content

Conversation

Anyitechs
Copy link
Contributor

Following the work (#3718 and #3925) that introduced uploading coverage from no-corpus fuzzing runs into codecov in CI. This PR focuses on uploading the CI-generated fuzz corpus coverage into codecov in CI.

Closes #3926

@ldk-reviews-bot
Copy link

ldk-reviews-bot commented Oct 10, 2025

🎉 This PR is now ready for review!
Please choose at least one reviewer by assigning them on the right bar.
If no reviewers are assigned within 10 minutes, I'll automatically assign one.
Once the first reviewer has submitted a review, a second will be assigned if required.

Copy link

codecov bot commented Oct 10, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.21%. Comparing base (7439528) to head (fdf6799).
⚠️ Report is 41 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4153      +/-   ##
==========================================
+ Coverage   88.63%   89.21%   +0.57%     
==========================================
  Files         180      180              
  Lines      135230   136553    +1323     
  Branches   135230   136553    +1323     
==========================================
+ Hits       119865   121829    +1964     
+ Misses      12594    12123     -471     
+ Partials     2771     2601     -170     
Flag Coverage Δ
fuzzing 31.41% <ø> (+9.64%) ⬆️
tests 88.63% <ø> (+0.15%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Anyitechs Anyitechs marked this pull request as draft October 10, 2025 18:42
Because each CI job runs on a fresh runner and can't share data between jobs. We rely on Github Actions upload-artifact and download-artifact to share the CI generated fuzz corpus, then replay them in the `contrib/generate_fuzz_coverage.sh` script to generate the coverage report.
@Anyitechs Anyitechs force-pushed the upload-fuzz-coverage branch from dc493c2 to fdf6799 Compare October 13, 2025 00:25
@Anyitechs Anyitechs marked this pull request as ready for review October 13, 2025 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upload CI-generated fuzz corpus coverage to codecov

2 participants